Selerix Developer Tools
Web Services (SOAP)
This section describes the steps required to launch a BenSelect enrollment session from within your application using a user ID and password for authentication. For single sign-on integrations, refer to the section that covers SAML integrations.
Integration development may begin only after the necessary information has been exchanged between your company and Selerix as discussed earlier. Selerix or your BenSelect group administrator will supply you with the information you need to authenticate and launch an enrollment. Web service integrations are most frequently authenticated using an agent user ID and password. When applicant data is preloaded to the group, however, the target applicant's user information may be used instead, depending on the Selerix agreement and enrollment group case setup.
The examples presented here assume you are using BenSelect only to capture enrollment data and not to manage post-enrollment data, which would require additional information in the outbound payload. Check with Selerix or your group administrator to see if enrollment business rules dictate additional data be included in the transmission.
To launch a Selerix enrollment, execute the appropriate web service remote procedure call by posting SOAP XML messages to BenSelect. Depending on the group configuration, SAML v1.1 may alternatively be used to perform a single sign-on authentication where web services are used for all other service requests. This section, however, focuses on enrollment integrations that use only web services.
When applicant data is pre-loaded on the BenSelect case, minimal information is required to authenticate and identify the target enrollee. If enrollee data has not been preloaded, you must furnish it and possibly other data before you can launch the enrollment session.
Regardless of how much data is required before you may begin, all applicant and enrollment data is packaged into a Selerix Data Transmittal XML structure, stored as a proprietary element in the SOAP XML, and posted to BenSelect as part of a SOAP message. Under the hood, the transmittal XML is merely a serialized version of a Selerix transmittal object. The transmittal, therefore, serves not only as a data container but as a dictionary as well, exposing all possible data members related to a BenSelect enrollment.
When enrollment completes, BenSelect posts the result of the enrollment session to a URL you specify. The SOAP message XML communicates whether the enrollment session was terminated with a successful enrollment completion or was interrupted and is incomplete. If the enrollment completed successfully, the message will also contain a Selerix transmittal XML in a Selerix proprietary element within the SOAP XML.
BenSelect is flexible and allows you to post a web services query at a later time to obtain enrollment data if that better suits your needs. Or, alternatively, you may use BenSelect reporting to deliver enrollment results in encrypted form using a SFTP drop point you specify from the BenSelect administration site.
Essentially, a web services-based enrollment requires constructing XML, converting strings, and posting XML via HTTP to BenSelect. Since most of the work required to accomplish this should be common knowledge for web developers, this documentation assumes familiarity with XML, SOAP and HTTPS. Therefore, the two proprietary aspects covered in this section are:
The essential steps to launch a Selerix BenSelect enrollment are described in the Web Services Basic Instructions topic.